Document yarn release, add .yarnrc & .eslintignore #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kylesuss
commented
Jun 3, 2019
|
|
||
| import MyComponent from "@storybook/design-system"; | ||
| import MyComponent from '@storybook/design-system'; |
There was a problem hiding this comment.
Prettier updated this.
shilman
approved these changes
Jun 3, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
.yarnrcfile lets us runyarn publishwithout having yarn assume that we want to push to the yarn registry.Let me know if the docs I added make sense or could be formatted any better.
I made a bit of a mess doing this publishing & unpublishing packages/changelogs, but I think I have it cleaned up now. There might be a slight issue once the next version is released as NPM won't allow
0.0.15since I have already published & unpublished it (it had nothing in it). Thepackage.jsoncurrently says0.0.14so I thinkautois going to think that the next version is0.0.15and try to push to NPM, but that will fail. @shilman any thoughts on how to fix this?